Skip to content

Moniker changes for 2508 #3781

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 13, 2025

Conversation

ManikaDhiman
Copy link
Contributor

No description provided.

Copy link
Contributor

@ManikaDhiman : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit f7bde1e:

⚠️ Validation status: warnings

File Status Preview URL Details
azure-local/known-issues.md ⚠️Warning Details
azure-local/security-update/security-update.md ⚠️Warning Details
azure-local/docfx.json ✅Succeeded
azure-local/whats-new.md ✅Succeeded

azure-local/known-issues.md

  • Line 438, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Fixed issues''. Each second level heading (H2) in an article must be unique.
  • Line 442, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Known issues in this release''. Each second level heading (H2) in an article must be unique.
  • Line 450, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Known issues from previous releases''. Each second level heading (H2) in an article must be unique.
  • Line 476, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Fixed issues''. Each second level heading (H2) in an article must be unique.
  • Line 487, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Known issues in this release''. Each second level heading (H2) in an article must be unique.
  • Line 495, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Known issues from previous releases''. Each second level heading (H2) in an article must be unique.

azure-local/security-update/security-update.md

  • Line 437, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Improvements''. Each second level heading (H2) in an article must be unique.
  • Line 459, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Known issues''. Each second level heading (H2) in an article must be unique.
  • Line 493, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'File list''. Each second level heading (H2) in an article must be unique.
  • Line 501, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Improvements''. Each second level heading (H2) in an article must be unique.
  • Line 516, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Known issues''. Each second level heading (H2) in an article must be unique.
  • Line 526, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'File list''. Each second level heading (H2) in an article must be unique.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

Copy link
Contributor

Learn Build status updates of commit 4a0c40a:

✅ Validation status: passed

File Status Preview URL Details
azure-local/docfx.json ✅Succeeded
azure-local/known-issues.md ✅Succeeded
azure-local/security-update/security-update.md ✅Succeeded
azure-local/whats-new.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Contributor

PRMerger Results

Issue Description
Json File This PR contains json file(s).

@v-dirichards
Copy link
Contributor

@alkohli @v-sissondan

Can you review the proposed changes?

If you approve the new content in this PR, the commits must be moved to the private repository for automated checks and publishing. After you move the commits, close this PR (#please-close). If you need help moving the commits, contact the publicprs alias.

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged Tracking label for the PR review team label Aug 6, 2025
@alkohli
Copy link
Contributor

alkohli commented Aug 13, 2025

#sign-off

@ShannonLeavitt ShannonLeavitt merged commit ea49a59 into MicrosoftDocs:main Aug 13, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants